System Keys
Some Excelerator modules require Sage system keys to be set up. These must be entered in Sage by a Sage system administrator.
Some of these will be described under the help sections for the module. System keys relating to multiple modules are described below.
INTUSER
In some instances, Sage records the name of the Sage user who entered the batch. As Excelerator does not log into Sage, there is no Sage username available to record against the batch. Instead, Excelerator uses the value held in this system key as the user name.
CODVERSION
Excelerator has to be told if it is being used with Sage 500 version 6 or higher, or Sage 1000 2.1 or higher. The system CODVERSION must be set in every Sage company being used. Values are:
|
Sage Product |
Sage Version |
CODVERSION value |
|
500 |
< 6 |
5 |
|
500 |
6 |
6 |
|
500 |
7 |
7 |
|
500 |
7.1 |
7 |
|
1000 |
2.0 |
2.0 |
|
1000 |
2.1 |
2.1 |
|
1000 |
2.2 |
2.2 |
|
1000 |
2.3 |
2.3 |
|
1000 |
3.0 |
3.0 |
Project System Keys
Excelerator also has to be told about any Sage projects that have been activated in Sage.
Note: You should first check that Excelerator supports the project at http://www.codis.co.uk/SupportedProjects.htm.
As Excelerator cannot access Sage's project configuration, system keys need to be set to tell Excelerator which projects are activated. These must be set in every Sage company.
The system keys are CODDA<DA number>. For example CODDA0567, CODDA1484.
Some projects are mandatory in Sage 1000, and these projects will be activated by setting the CODVERSION to a value that indicates Sage 1000 is being used.
Some standard Excelerator modules need to know the name of the current Sage company. (This is not available from the connection details.) In these cases, the system key CODCOMPANY must be set up on each of the Sage databases. It should hold the name of the company as entered in the Sage Working directories utility.